Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current rss.js code always embeds non-SSL (http:) links in the feed data. This is not a good thing because in typical acralyzer installations, access to the bug reports requires transmitting the CouchDB administrator login/password over the wire. Also, crash reports may contain sensitive user data.
I experimented with adding SSL autodetection to rss.js, but encountered the following limitations:
All three problems can be addressed by using Atom instead, and specifying relative URLs in the feed. So I am submitting atom.js, accessed via
https://HOST/acra-PROJECT/_design/acra-storage/_list/atom/recent-items?descending=true
. i.e. just replace "rss" with "atom" in the URL.The output from this code passes the w3c.org feed validator. There is one non-fatal warning regarding the use of relative URLs in the "self" link, which is allowed but discouraged.
atom.js incorporates @halkeye's pending fixes from bug #10.
See here for background discussion on the CouchDB list; there are additional posts in the thread.